PowerChute Network Shutdown
Release Notes

Problem/Issue:
When several actions are selected for the same event, and the actions all have the same delay time, some actions do not occur.
Solution: Threading issues in Java occasionally cause the actions to interfere with each other. Use different delay times for each action.

Problem/Issue:
During the installation, you receive an error message that PowerChute Network Shutdown is unable to register with the Management Card.
Solution: In some cases, the installation program registers PowerChute Network Shutdown with the Network Management Card, but is unable to confirm that it is registered. Check the IP address list on the Network Management Card by opening the Network Management Card user interface and selecting the PowerChute menu item. If your computer IP address does not appear on the list, add it manually using the following steps:

1. Type the IP address of the PowerChute Network Shutdown server in the Add Client IP Address field.
2. Select the Add button.

Problem/Issue:
Updates to the PowerChute Network Shutdown configuration do not appear on the Configure Events page.
Solution: Memory caching can cause old versions of the Configure Events page to be displayed instead of the updated version. Refresh the frame, or disable caching on the web browser.

Problem/Issue:
Occasionally, after you enter the user name and password, the user interface does not respond.
Solution: Select Stop and then Refresh.

Problem/Issue:
After you remove PowerChute Network Shutdown, the Network Management Card still has the server IP address.
Solution: To remove IP addresses, select each address from the Configured Client IP Addresses list, and select Remove.

Problem/Issue:
PowerChute Network Shutdown is already installed, and you want to monitor a different Network Management Card.
Solution: Use the stand-alone configuration utility described in PowerChute Network Shutdown Configuration Utility in the Installation Guide.

Note: The configuration utility cannot be used with multiple Smart-UPS devices, multiple Symmetra devices, or a Parallel Silcon UPS.

Problem/Issue:
Updates to the PowerChute Network Shutdown configuration do not appear on the Configure Events page.
Solution: Memory caching can cause old versions of the Configure Events page to be displayed instead of the updated version. Refresh the frame or disable caching on the web browser.

Problem/Issue:
PowerChute Network Shutdown has an event for "Bypass: Maintenance" but no event for a bypass caused by a UPS fault.
Solution: The "Bypass: Maintenance" event occurs in response to any type of UPS bypass.

Problem/Issue:
"Battery: Removed" and "UPS Module: Removed" events are logged in the PowerChute Network Shutdown event log when you remove the Main Intelligence Module from the Symmetra Power Array.
Solution: No action is required. PowerChute Network Shutdown recalculates the number of batteries and modules each time the Main Intelligence Module is removed and replaced.

Problem/Issue:
Command files do not run properly when called by PowerChute Network Shutdown. The command file stops before all of the statements have executed.
Solution: The command file must use the @START command to run executable programs, and use the full path name of the program. Path names that include spaces must be enclosed in quotes. Arguments for the executable must be outside the quotes.  

For example, if you must run Hyperterminal and Backup in your command file, use the syntax:

@START "c:\Program Files\Windows NT\hypertrm.exe" arguments
@START c:\Winnt\system32\backup  arguments

Problem/Issue:
A PowerChute Network Shutdown client that acquires its IP address through DHCP will lose communications with the Network Management Card when the client renews its DHCP address lease and acquires a different IP address.
Solution: Do not use PowerChute Network Shutdown on systems running DHCP. Each system using PowerChute Network Shutdown must have a permanent IP address.

Problem/Issue:
After installing PowerChute Network Shutdown, a directory called tmpjex01 (or a similar name) is in the Temp directory or at the root.
Solution: Delete this directory.

Problem/Issue:
After a graceful shutdown by PowerChute Network Shutdown, the server fails to turn on when utility power is restored.

Due to changes in the power management feature in Windows XP SP1 and Windows 2003, some servers with an ACPI (Advanced Configuration and Power Interface) BIOS will not turn on when utility power is restored after an outage. The following is an example of what may occur:

• A server is attached to an APC UPS and running PowerChute Network Shutdown. PowerChute Network Shutdown is configured to shut down the operating system when the UPS has been on battery for a specific time.
• When the utility power fails, causing the on-battery event, PowerChute Network Shutdown commands the operating system to shut down gracefully.
• Because ACPI power management is controlled by the operating system rather than by the BIOS, when the operating system completes its graceful shutdown, it commands the server to turn off.
• The UPS remains on battery until its shutdown delay time has expired. When utility power is restored, the UPS provides power; the server does not turn on.

Problem/Issue:
You are unable to install the software, or the software is not working properly.
Solution: Both of these problems can be caused by not having Administrator privileges for the network while installing the software. You need Administrator privileges to install the software properly.

To start, stop, or remove PowerChute Network Shutdown on these operating systems and for other background information, see the respective sections in the Installation Guide:

• Using PowerChute Network Shutdown on Solaris
• Using PowerChute Network Shutdown on Linux
• Using PowerChute Network Shutdown on Novell NetWare